Sidelink downlink control information configuration

ABSTRACT

A wireless device receives a sidelink (SL) downlink control information (DCI). The SL DCI indicates: one or more first frequency domain resources; one or more first time domain resources; and a periodicity. One or more SL control information (SCI) indicating the periodicity and one or more first SL transmissions is transmitted via a first set of SL resources. The first set of SL resources are determined based on the one or more first frequency domain resources and the one or more first time domain resources. One or more second SL transmissions are transmitted via a second set of SL resources determined based on: the one or more first frequency domain resources; the one or more first time domain resources; and the periodicity.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/954,291, filed Dec. 27, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17 illustrates an example of a multi-beam multi-TRP scenario.

FIG. 18 illustrates a RLM-RS determination as per an aspect of anexample embodiment of the present disclosure.

FIG. 19 illustrates a deployment scenario of a multi-TRP operation asper an aspect of an example embodiment of the present disclosure.

FIG. 20A illustrates example parameters of an RLM-RS as per an aspect ofan example embodiment of the present disclosure.

FIG. 20B illustrates example parameters of a non-zero-power CSI-RS asper an aspect of an example embodiment of the present disclosure.

FIG. 21 is a signal flow diagram of an aspect of an example embodimentof the present disclosure.

FIG. 22 is a signal flow diagram of an aspect of an example embodimentof the present disclosure.

FIG. 23 is a signal flow diagram of an aspect of example embodiment ofthe present disclosure.

FIG. 24 illustrates a deployment scenario of a multi-TRP operation asper an aspect of an example embodiment of the present disclosure.

FIG. 25 illustrates a grouping in a multi-TRP scenario as per an aspectof an example embodiment of the present disclosure.

FIG. 26 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WI-FI® or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNB s 162 may include three sets ofantennas to respectively control three cells (or sectors). Together, thecells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage tothe UEs 156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3 , the SDAPs 215 and 225 may perform QoS flowhandling. The UE 210 may receive services through a PDU session, whichmay be a logical connection between the UE 210 and a DN. The PDU sessionmay have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) maymap IP packets to the one or more QoS flows of the PDU session based onQoS requirements (e.g., in terms of delay, data rate, and/or errorrate). The SDAPs 215 and 225 may perform mapping/de-mapping between theone or more QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3 , PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3 , the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3 , the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3 , the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3 ), add correspondingheaders, and forward their respective outputs to the next lower layer.For example, the PDCP 224 may perform IP-header compression andciphering and forward its output to the RLC 223. The RLC 223 mayoptionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs and may attach a MAC subheader to an RLC PDU to forma transport block. In NR, the MAC subheaders may be distributed acrossthe MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders maybe entirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages        used to page a UE whose location is not known to the network on        a cell level;    -   a broadcast control channel (BCCH) for carrying system        information messages in the form of a master information block        (MIB) and several system information blocks (SIBs), wherein the        system information messages may be used by the UEs to obtain        information about how a cell is configured and how to operate        within the cell;    -   a common control channel (CCCH) for carrying control messages        together with random access;    -   a dedicated control channel (DCCH) for carrying control messages        to/from a specific the UE to configure the UE; and    -   a dedicated traffic channel (DTCH) for carrying user data        to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   -   a paging channel (PCH) for carrying paging messages that        originated from the PCCH;    -   a broadcast channel (BCH) for carrying the MIB from the BCCH;    -   a downlink shared channel (DL-SCH) for carrying downlink data        and signaling messages, including the SIBs from the BCCH;    -   an uplink shared channel (UL-SCH) for carrying uplink data and        signaling messages; and    -   a random access channel (RACH) for allowing a UE to contact the        network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from        the BCH;    -   a physical downlink shared channel (PDSCH) for carrying downlink        data and signaling messages from the DL-SCH, as well as paging        messages from the PCH;    -   a physical downlink control channel (PDCCH) for carrying        downlink control information (DCI), which may include downlink        scheduling commands, uplink scheduling grants, and uplink power        control commands;    -   a physical uplink shared channel (PUSCH) for carrying uplink        data and signaling messages from the UL-SCH and in some        instances uplink control information (UCI) as described below;    -   a physical uplink control channel (PUCCH) for carrying UCI,        which may include HARQ acknowledgments, channel quality        indicators (CQI), pre-coding matrix indicators (PMI), rank        indicators (RI), and scheduling requests (SR); and    -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6 , a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE's serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 μs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8 . An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8 . An NRcarrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers.Such a limitation, if used, may limit the NR carrier to 50, 100, 200,and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz,respectively, where the 400 MHz bandwidth may be set based on a 400 MHzper carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE's receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9 , the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9 , the UE may switch from the BWP 902 to the BWP 904 at aswitching point 908. The switching at the switching point 908 may occurfor any suitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPcell1011, an Scell1012, and an Scell1013. The PUCCH group 1050 includesthree downlink CCs in the present example: a Pcell1051, an Scell1052,and an Scell1053. One or more uplink CCs may be configured as aPcell1021, an Scell1022, and an Scell1023. One or more other uplink CCsmay be configured as a primary Scell (PSCell) 1061, an Scell1062, and anScell1063. Uplink control information (UCI) related to the downlink CCsof the PUCCH group 1010, shown as UCI 1031, UCI 1032, and UCI 1033, maybe transmitted in the uplink of the Pcell1021. Uplink controlinformation (UCI) related to the downlink CCs of the PUCCH group 1050,shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted in theuplink of the PScell1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the Pcell1021 and the PScell1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS)/physical broadcast channel (PBCH) block thatincludes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE's transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_idwhere s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id<80), f_id may be an index ofthe PRACH occasion in the frequency domain (e.g., 0≤f_id<8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE'sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceld). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1320 may be transmitted in an uplink transmission by the UE. Msg A1320 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1350 after or in response to transmittingthe Msg A 1320. The Msg B 1350 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE's RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1350.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a size and alocation of the CORESET in the time-frequency domain. In the example ofFIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at thefirst symbol in a slot. The first CORESET 1401 overlaps with the secondCORESET 1402 in the frequency domain. A third CORESET 1403 occurs at athird symbol in the slot. A fourth CORESET 1404 occurs at the seventhsymbol in the slot. CORESETs may have a different number of resourceblocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15 , but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15 .

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For transmit processing, the PHY layermay perform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15 , a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15 , the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

FIG. 17 illustrates examples of device-to-device (D2D) communication, inwhich there is a direct communication between wireless devices. In anexample, D2D communication may be performed via a sidelink (SL). Thewireless devices may exchange sidelink communications via a sidelinkinterface (e.g., a PC5 interface). Sidelink differs from uplink (inwhich a wireless device communicates to a base station) and downlink (inwhich a base station communicates to a wireless device). A wirelessdevice and a base station may exchange uplink and/or downlinkcommunications via a user plane interface (e.g., a Uu interface).

As shown in the figure, wireless device #1 and wireless device #2 may bein a coverage area of base station #1. For example, both wireless device#1 and wireless device #2 may communicate with the base station #1 via aUu interface. Wireless device #3 may be in a coverage area of basestation #2. Base station #1 and base station #2 may share a network andmay jointly provide a network coverage area. Wireless device #4 andwireless device #5 may be outside of the network coverage area.

In-coverage D2D communication may be performed when two wireless devicesshare a network coverage area. Wireless device #1 and wireless device #2are both in the coverage area of base station #1. Accordingly, they mayperform an in-coverage intra-cell D2D communication, labeled as sidelinkA. Wireless device #2 and wireless device #3 are in the coverage areasof different base stations, but share the same network coverage area.Accordingly, they may perform an in-coverage inter-cell D2Dcommunication, labeled as sidelink B. Partial-coverage D2Dcommunications may be performed when one wireless device is within thenetwork coverage area and the other wireless device is outside thenetwork coverage area. Wireless device #3 and wireless device #4 mayperform a partial-coverage D2D communication, labeled as sidelink C.Out-of-coverage D2D communications may be performed when both wirelessdevices are outside of the network coverage area. Wireless device #4 andwireless device #5 may perform an out-of-coverage D2D communication,labeled as sidelink D.

Sidelink communications may be configured using physical channels, forexample, a physical sidelink broadcast channel (PSBCH), a physicalsidelink feedback channel (PSFCH), a physical sidelink discovery channel(PSDCH), a physical sidelink control channel (PSCCH), and/or a physicalsidelink shared channel (PSSCH). PSBCH may be used by a first wirelessdevice to send broadcast information to a second wireless device. PSBCHmay be similar in some respects to PBCH. The broadcast information maycomprise, for example, a slot format indication, resource poolinformation, a sidelink system frame number, or any other suitablebroadcast information. PSFCH may be used by a first wireless device tosend feedback information to a second wireless device. The feedbackinformation may comprise, for example, HARQ feedback information. PSDCHmay be used by a first wireless device to send discovery information toa second wireless device. The discovery information may be used by awireless device to signal its presence and/or the availability ofservices to other wireless devices in the area. PSCCH may be used by afirst wireless device to send sidelink control information (SCI) to asecond wireless device. PSCCH may be similar in some respects to PDCCHand/or PUCCH. The control information may comprise, for example,time/frequency resource allocation information (RB size, a number ofretransmissions, etc.), demodulation related information (DMRS, MCS, RV,etc.), identifying information for a transmitting wireless device and/ora receiving wireless device, a process identifier (HARQ, etc.), or anyother suitable control information. The PSCCH may be used to allocate,prioritize, and/or reserve sidelink resources for sidelinktransmissions. PSSCH may be used by a first wireless device to sendand/or relay data and/or network information to a second wirelessdevice. PSSCH may be similar in some respects to PDSCH and/or PUSCH.Each of the sidelink channels may be associated with one or moredemodulation reference signals. Sidelink operations may utilize sidelinksynchronization signals to establish a timing of sidelink operations.Wireless devices configured for sidelink operations may send sidelinksynchronization signals, for example, with the PSBCH. The sidelinksynchronization signals may include primary sidelink synchronizationsignals (PSSS) and secondary sidelink synchronization signals (SSSS).

Sidelink resources may be configured to a wireless device in anysuitable manner. A wireless device may be pre-configured for sidelink,for example, pre-configured with sidelink resource information.Additionally or alternatively, a network may broadcast systeminformation relating to a resource pool for sidelink. Additionally oralternatively, a network may configure a particular wireless device witha dedicated sidelink configuration. The configuration may identifysidelink resources to be used for sidelink operation (e.g., configure asidelink band combination).

The wireless device may operate in different modes, for example, anassisted mode (which may be referred to as mode 1) or an autonomous mode(which may be referred to as mode 2). Mode selection may be based on acoverage status of the wireless device, a radio resource control statusof the wireless device, information and/or instructions from thenetwork, and/or any other suitable factors. For example, if the wirelessdevice is idle or inactive, or if the wireless device is outside ofnetwork coverage, the wireless device may select to operate inautonomous mode. For example, if the wireless device is in a connectedmode (e.g., connected to a base station), the wireless device may selectto operate (or be instructed by the base station to operate) in assistedmode. For example, the network (e.g., a base station) may instruct aconnected wireless device to operate in a particular mode.

In an assisted mode, the wireless device may request scheduling from thenetwork. For example, the wireless device may send a scheduling requestto the network and the network may allocate sidelink resources to thewireless device. Assisted mode may be referred to as network-assistedmode, gNB-assisted mode, or base station-assisted mode. In an autonomousmode, the wireless device may select sidelink resources based onmeasurements within one or more resource pools (for example,pre-configure or network-assigned resource pools), sidelink resourceselections made by other wireless devices, and/or sidelink resourceusage of other wireless devices.

To select sidelink resources, a wireless device may observe a sensingwindow and a selection window. During the sensing window, the wirelessdevice may observe SCI transmitted by other wireless devices using thesidelink resource pool. The SCIs may identify resources that may be usedand/or reserved for sidelink transmissions. Based on the resourcesidentified in the SCIs, the wireless device may select resources withinthe selection window (for example, resource that are different from theresources identified in the SCIs). The wireless device may transmitusing the selected sidelink resources.

FIG. 18 illustrates an example of a resource pool for sidelinkoperations. A wireless device may operate using one or more sidelinkcells. A sidelink cell may include one or more resource pools. Eachresource pool may be configured to operate in accordance with aparticular mode (for example, assisted or autonomous). The resource poolmay be divided into resource units. In the frequency domain, eachresource unit may comprise, for example, one or more resource blockswhich may be referred to as a sub-channel. In the time domain, eachresource unit may comprise, for example, one or more slots, one or moresubframes, and/or one or more OFDM symbols. The resource pool may becontinuous or non-continuous in the frequency domain and/or the timedomain (for example, comprising contiguous resource units ornon-contiguous resource units). The resource pool may be divided intorepeating resource pool portions. The resource pool may be shared amongone or more wireless devices. Each wireless device may attempt totransmit using different resource units, for example, to avoidcollisions.

Sidelink resource pools may be arranged in any suitable manner. In thefigure, the example resource pool is non-contiguous in the time domainand confined to a single sidelink BWP. In the example resource pool,frequency resources are divided into a Nf resource units per unit oftime, numbered from zero to Nf−1. The example resource pool may comprisea plurality of portions (non-contiguous in this example) that repeatevery k units of time. In the figure, time resources are numbered as n,n+1 . . . n+k, n+k+1 . . . , etc.

A wireless device may select for transmission one or more resource unitsfrom the resource pool. In the example resource pool, the wirelessdevice selects resource unit (n,0) for sidelink transmission. Thewireless device may further select periodic resource units in laterportions of the resource pool, for example, resource unit (n+k,0),resource unit (n+2 k,0), resource unit (n+3 k,0), etc. The selection maybe based on, for example, a determination that a transmission usingresource unit (n,0) will not (or is not likely) to collide with asidelink transmission of a wireless device that shares the sidelinkresource pool. The determination may be based on, for example, behaviorof other wireless devices that share the resource pool. For example, ifno sidelink transmissions are detected in resource unit (n−k,0), thenthe wireless device may select resource unit (n,0), resource (n+k,0),etc. For example, if a sidelink transmission from another wirelessdevice is detected in resource unit (n−k,1), then the wireless devicemay avoid selection of resource unit (n,1), resource (n+k,1), etc.

Different sidelink physical channels may use different resource pools.For example, PSCCH may use a first resource pool and PSSCH may use asecond resource pool. Different resource priorities may be associatedwith different resource pools. For example, data associated with a firstQoS, service, priority, and/or other characteristic may use a firstresource pool and data associated with a second QoS, service, priority,and/or other characteristic may use a second resource pool. For example,a network (e.g., a base station) may configure a priority level for eachresource pool, a service to be supported for each resource pool, etc.For example, a network (e.g., a base station) may configure a firstresource pool for use by unicast UEs, a second resource pool for use bygroupcast UEs, etc. For example, a network (e.g., a base station) mayconfigure a first resource pool for transmission of sidelink data, asecond resource pool for transmission of discovery messages, etc.

In an example, a wireless device may support one or more DCI formats,wherein a DCI format may comprise one or more DCI fields. Depending on apurpose of the DCI format, a different combinations of DCI fields may beexpected. For example, a DCI format 1_0 used for a downlink datascheduling may comprise a frequency domain resource allocation, aPDSCH-to-HARQ feedback timing indicator (e.g., a time offset between aPDSCH to a PUCCH for HARQ-ACK feedback) and a PUCCH resource indicator.A DCI format 0_0 used for an uplink data scheduling may comprise afrequency domain resource allocation, a transmission power control (TPC)for PUSCH, and UL/SUL indicator. A sidelink DCI comprising resourceassignments for one or more sidelink transmissions. The sidelink DCI maynot need a TPC field or a PUCCH resource indicator depending on HARQ-ACKfeedback configuration/option. A wireless device may need to know a DCIsize of a DCI format before it attempts to decode a DCI in response toreceiving the DCI via a physical control channel (PDCCH). The wirelessdevice may need to perform a first decoding on a first PDCCH candidatewith a first DCI size. The wireless device may need to perform a seconddecoding on a second PDCCH candidate with a second DCI size. To maintainUE complexity reasonably, it is necessary to maintain a number of DCIsizes that the wireless device needs to perform decoding on is limited.While the wireless device may support more number of DCI formats andmaintain a reasonable decoding complexity, a DCI size alignment amongone or more DCI formats where the wireless device may append zeros ortruncate a few bits from a DCI format to align a DCI size to another DCIformat may be performed.

In existing technologies, a wireless device may support a limited numberof downlink control information (DCI) sizes (e.g., K sizes) whereas thewireless device may support a larger number of DCI formats (e.g., M DCIformats). The wireless device may operate a sidelink operation on asidelink cell. A base station may schedule resources for the sidelinkcell via a scheduling cell using a sidelink DCI. For example, thesidelink DCI may be transmitted via a physical downlink control channel(PDCCH) based on a sidelink DCI format. The wireless device may appendzeros to the sidelink DCI format until a DCI size of the sidelink DCIformat becomes equal to a DCI size of DCI format 0_0 (e.g., a DCI formatused for scheduling an uplink grant).

A wireless device may determine a DCI size of a DCI format based on anactive downlink, an active uplink or an active sidelink bandwidth part(BWP) depending on a purpose of the DCI format. For example, thewireless device may determine a DCI size of a DCI format 0_0 based onthe active uplink BWP. When the wireless device switches from a firstuplink BWP to a second uplink BWP, a DCI size of the DCI format 0_0 maybe also adjusted/changed. When the wireless device aligns a DCI size ofthe sidelink DCI format with the DCI format 0_0, the wireless device mayneed to adjust/change the DCI size of the sidelink DCI format inresponse to an uplink BWP switching. This may lead to unnecessary DCIsize changes of the sidelink DCI format and may lead serviceinterruption due to misalignment between the base station and thewireless device.

In an example, a DCI size of a sidelink DCI format may be determinedbased on an active sidelink BWP. A base station may configure areference DCI format for the sidelink DCI format, wherein a wirelessdevice may add zeros either to the reference DCI format or the sidelinkDCI format to align DCI sizes of both to be the same. When a wirelessdevice switches from a first downlink BWP to a second downlink BWP, aDCI size of the reference DCI format may change. For example, thereference DCI format may become larger or smaller than the DCI size ofthe sidelink DCI format. In the second downlink BWP, the reference DCIformat may be either considerably smaller or larger than a DCI size ofthe sidelink DCI format before padding any zeros, and thus may not be agood to perform a DCI size alignment between the reference DCI formatand the sidelink DCI format in the second downlink BWP. Existingtechnologies may not provide flexibility to configure a good referenceDCI format for a sidelink DCI format to align DCI sizes wherein theconfiguration may allow minimal zeros padding or avoid unnecessarilytruncation of the sidelink DCI format.

In an example, a base station may configure a reference DCI format foreach downlink BWP of a plurality of downlink BWPs of a scheduling cellfor a sidelink cell. FIG. 19 illustrates an example. For example, a DCIsize of a sidelink DCI format may not change with a downlink BWPswitching as the DCI size of the sidelink DCI format may be determinedbased on an active sidelink BWP. In a DL BWP 0, the base station mayconfigure DCI format 1 as the reference DCI format as it may not bedesirable to change a DCI size of the DCI format 0. In a downlink BWP 1,as the DCI size of DCI format 0 becomes larger than the DCI size of thesidelink DCI format while a DCI size of DCI format 1 becomes much largerthan the DCI size of the sidelink DCI format, the base station mayconfigure DCI format 1 as the reference DCI format. In the example, thewireless device appends zeros to the sidelink DCI format (DCI 3) untilthe DCI 3 becomes equal size to the DCI 1 in the DL BWP 0, and appendszeros to the DCI 3 until the DCI 3 becomes equal size to the DCI 0 inthe DL BWP 1.

In an example, a DCI size of a sidelink DCI format may be determinedbased on an active sidelink BWP. Depending on an active sidelink BWP, adesirable reference DCI format may be different. For example, a basestation may configure a first reference DCI format for a first sidelinkBWP. The base station may configure a second reference DCI format for asecond sidelink BWP. FIG. 20 illustrates an example. For example, awireless device may be configured with a first sidelink BWP (SL BWP1)and a second sidelink BWP (SL BWP2) in a sidelink cell. A sidelink DCIformat (e.g., DCI 3) may have a different DCI size depending on anactive sidelink BWP. For example, in the SL BWP1, a DCI size of the DCI3 is smaller than a DCI format 1 (DCI 1) whereas larger than a DCIformat 0 (DCI 0). In the SL BWP2, a DCI size of the DCI3 is smaller thanDCI 0. In the SL BWP1, a reference DCI format is configured as DCI 1 astruncating bits from the sidelink DCI format is not desirable. Moreover,changing a DCI size of DCI 0 (e.g., a fallback DCI format) may not bedesirable. The wireless device may add zeros to the DCI 3 until the DCI3 becomes equal size to the DCI 1 in the SL BWP1. The base station mayconfigure DCI 0 as a reference DCI format in SL BWP2 as the size of DCI3becomes smaller than the size of DCI 0.

Embodiments allow flexibility of configuring a reference DCI format fora sidelink DCI format, depending on an active downlink BWP and/or anactive sidelink BWP. Embodiments allow minimal zero padding and/or avoidunnecessarily DCI format bits truncation. While supporting existing UEcapabilities, embodiments allow enhanced performance with minimizedextra padding bits and/or truncated bits in one or more DCI formats fora DCI size alignment.

In an example, a wireless device may support up to K different downlinkcontrol information (DCI) sizes while supporting M different DCI formats(e.g., K<=M). For example, the wireless device may support up to 4different DCI sizes whereas the wireless device may support a DCI formatof 0_0, 1_0, 0_1, 1_1, 2_0, 2_1, 2_2, 2_3, 3_0 and/or 3_1. The wirelessdevice and a base station may align one or more DCI formats to a firstDCI size based on one or more rules and/or one or more configurationparameters. For example, the wireless device and the base station mayassume a same first DCI size between a DCI format of 0_0 and 0_1. Thewireless device and the base station may assume a same second DCI sizebetween a DCI format 2_0, 2_3 and 0_1.

In an example, a wireless device may support one or more sidelink cells,wherein a base station may configure a gNB-assisted or a mode 1 sidelinkoperation for the one or more sidelink cells. The base station mayschedule one or more sidelink resources via a sidelink DCI format for asidelink cell. For example, a first sidelink DCI may be used for a firstsidelink cell, wherein the first sidelink DCI is transmitted/scheduledvia a first cell. For example, a second sidelink DCI may be used for asecond sidelink cell, wherein the second sidelink DCI istransmitted/schedule via a second cell. The first sidelink DCI and/orthe second sidelink DCI may be based on a first sidelink DCI format(e.g., DCI format 3_0) and/or a second sidelink DCI format (e.g., DCIformat 3_1). A wireless device may support up to K different DCI sizesfor a cell. The wireless device may support up to M different DCIformats for the cell. A base station may configure a reference DCIformat for a DCI format for each downlink bandwidth part of the cell.For example, in a PDCCH-Config of a downlink bandwidth configuration ofthe cell, the base station may indicate one or more pairs of {areference DCI format, a target DCI format} (or {a target DCI format, areference DCI format}). In receiving the one or more pairs of theparameters, the wireless device may determine a first DCI size of thetarget DCI format based on the target DCI format and the reference DCIformat. Additionally and optionally, the wireless device may determine asecond DCI size of the reference DCI format based on the target DCIformat and the reference DCI format. For example, the first DCI size maybe same as to the second DCI size. For example, the first DCI may besame as to a DCI size of the reference DCI format, assuming the DCI sizeof the reference DCI format may be determined without considering thetarget DCI format. In an example, a base station may configure one ormore search spaces for sidelink DCI based on one or more sidelink DCIformats. The base station may configure a reference DCI format in eachsearch space of the one or more search spaces where sidelink DCI isconfigured to be monitored. In response to the configuration in the eachsearch space, a wireless device may perform a DCI size alignmentprocess.

In an example, a base station may configure one or more pairs of {atarget DCI format, a reference DCI format} for each search spaceconfiguration for a cell where the wireless device is configured tomonitor the target DCI format. In the example, the base station mayconfigure a reference DCI format in the each search space configurationin addition to one or more DCI formats monitored on the search space.The wireless device may interpret this as the one or more pairs of {atarget DCI format for each one from the one or more DCI formats, thereference DCI format}. For example, a search space may be configured tomonitor a DCI format 3_0 and/or DCI format 3_1. A reference DCI formatof 0_1 may be configured for the search space. The wireless device mayalign DCI sizes between DCI format 3_0 and/or DCI format 3_1 first. Thewireless device may align DCI sizes between DCI format 3_0/3_1 and thereference DCI format. The wireless device may determine a first DCI sizeof the target DCI format based on one or more first DCI sizes of thetarget DCI format and one or more second DCI sizes of the reference DCIformat in one or more search spaces and in one or more downlinkbandwidth parts. For example, the wireless device may determine a secondDCI size of the reference DCI format by taking a largest DCI size fromthe second one or more DCI sizes of the reference DCI format in the oneor more search spaces and in the one or more downlink bandwidth parts.The one or more search spaces may be determined where the wirelessdevice is configured to monitor the reference DCI format in the one ormore search spaces. The one or more downlink bandwidth parts may bedetermined where the wireless device is configured with the one or moresearch spaces in the one or more downlink bandwidth parts.

For example, the wireless device may determine a third DCI size of thetarget DCI format by taking a largest DCI size from the first one ormore DCI sizes of the target DCI format in the one or more search spacesand in the one or more sidelink bandwidth parts. The one or more searchspaces may be determined where the wireless device is configured tomonitor the target DCI format in the one or more search spaces. The oneor more sidelink bandwidth parts may be determined where the wirelessdevice is configured to operate sidelink operation based on the targetDCI format via the cell.

In an example, a base station may configure a reference DCI format for atarget sidelink DCI format for a downlink bandwidth part of a pluralityof downlink bandwidth parts of a scheduling cell, wherein the basestation may transmit one or more sidelink DCIs via the scheduling cellto a wireless device for a sidelink cell. The wireless device mayoperate a mode 1 or gNB-assisted sidelink operation on the sidelink cellbased on the one or more sidelink DCIs. The wireless device may assumethat at least a search space is configured with the reference DCI formatin the downlink bandwidth part of the plurality of downlink bandwidthparts. The wireless device may determine a first DCI size based on areference DCI format on an active downlink bandwidth part, wherein thefirst DCI size is determined as a largest DCI size from one or morefirst DCI sizes of the reference DCI format in one or more search spacesof the active downlink bandwidth part. The wireless device may determinea second DCI size of the target sidelink DCI format for the activedownlink bandwidth part based on a current active sidelink bandwidthpart (BWP). The wireless device may determine a third DCI size for thetarget DCI format and/or the reference DCI format on the current activeDL BWP based on the first DCI size and/or the second DCI size.

For example, the wireless device may determine the third DCI size as thefirst DCI size. In case, the second DCI size is larger than the firstDCI size, the wireless device may perform one or more of the followings.For example, the wireless device may assume that the target sidelink DCIformat is not valid anymore and may disable, suspend, release and/ordeactivate the mode 1 or the gNB-assisted sidelink operation of asidelink cell. In response to disable, suspend, release and/ordeactivate the mode 1 operation, the wireless device may autonomouslyswitch to a mode 2 or a UE initiated mode of operation. The wirelessdevice may select one or more resources for sidelink transmissionswithout relying on sidelink DCIs in the mode 2 or the UEinitiated/UE-autonomous mode of sidelink operation. The wireless devicemay not perform sidelink operation until the base station mayreconfigure operation mode for the sidelink cell.

For example, the wireless device may truncate one or more bits from thetarget DCI format until a DCI size of the truncated sidelink DCI formatis equal to the third DCI size. The wireless device may truncate the oneor more bits from a most significant bits of the target DCI format or aleast significant bits of the target DCI format. For example, thewireless device may select a second reference DCI format wherein a DCIsize of the second reference DCI format is equal to or larger than thesecond DCI size. The wireless device may ignore the configured referenceDCI format in such a case, and may take the second reference DCI formatinstead. For example, the wireless device may determine the third DCIsize as the second DCI size in such case. The wireless device maymonitor the sidelink DCI format if a number of DCI sizes of allmonitored DCI formats on an active downlink BWP of a scheduling cellwould be smaller than or equal to a number of allowed DCI sizes by a UEcapability for the scheduling cell. Otherwise, the wireless device maynot monitor the sidelink DCI format. When the wireless device may notmonitor the sidelink DCI format, the wireless device may maintain a mode1 or a gNB-assisted sidelink operation on the sidelink cell. Thewireless device may rely on one or more configured grant resources forthe sidelink operation in such case.

In an example, a wireless device may be configured with a plurality ofsidelink BWPs for a sidelink cell. For each sidelink BWP of theplurality of sidelink BWPs, the wireless device may be configured withone or more search spaces for monitoring sidelink DCIs based on asidelink DCI format. For example, a first DCI size of the sidelink DCIformat via a first SL BWP may be same or different from a second DCIsize of the sidelink DCI format via a second SL BWP. A base station mayconfigure a reference DCI format for the sidelink DCI format for eachdownlink BWP regardless of sidelink BWP. The wireless device maydetermine a first DCI size of the reference DCI format, wherein thefirst DCI size is a largest DCI size monitored on a search space of acurrent active downlink bandwidth. The wireless device may determine asecond DCI size of the sidelink DCI format, wherein the second DCI sizeis a largest DCI size among DCI sizes of the sidelink DCI format basedon each sidelink BWP of the plurality of the sidelink BWPs.

In an example, a base station may configure a reference DCI format foreach sidelink BWP regardless of downlink BWP of a scheduling cell forthe sidelink cell. A wireless device may determine a first DCI size of asidelink DCI format for a active sidelink BWP based on a first referenceDCI format configured to the active sidelink BWP. The wireless devicemay determine a second DCI size of the reference DCI format, wherein thesecond DCI size is a largest DCI size of the reference DCI format ofsearch spaces in an active downlink BWP. The wireless device maydetermine a third DCI size where the third DCI size a larger DCI sizebetween the first DCI size and the second DCI size. In response toswitching from a first SL BWP to a second SL BWP, the wireless devicemay determine DCI size for the sidelink DCI format based on a secondreference DCI format configured to the second SL BWP.

In an example, a wireless device may switch from a first downlink BWP toa second downlink BWP based on a DCI or a timer for a cell. The wirelessdevice may be configured for monitoring a sidelink DCI format in thefirst and the second downlink BWP of the cell for a sidelink cell forsidelink operation via a mode 1 or a gNB-assisted operation. A basestation may configure a reference DCI format for the sidelink DCI formatfor the cell, wherein the reference DCI format may be used in eachdownlink BWP. For example, the wireless device may be configured tomonitor the reference DCI format in the first downlink BWP whereas thewireless device may be configured not to monitor the reference DCIformat in the second downlink BWP. For example, the second downlink BWPmay be a default BWP, where the default BWP may be used for a small BWPin response to an expiry of a bwp-inactivityTimer. The wireless devicemay determine a DCI size of the sidelink DCI format based on thereference DCI format in the first downlink BWP. The wireless device maynot be able to determine a DCI size of the sidelink DCI format based onthe reference DCI format in the second downlink BWP as the wirelessdevice may not monitor the reference DCI format when the second downlinkBWP is an active downlink BWP. In response to switching to the seconddownlink BWP, the wireless device may perform one or more followingbehaviors. For example, the wireless device may deactivate a mode 1 or agNB-assisted operation in response to the switching to the seconddownlink BWP. For example, the wireless device may ignore the referenceDCI format configuration, and may use a DCI size of the sidelink DCIformat without DCI size alignment. For example, the wireless device mayuse a DCI format configured to be monitored on the second downlink BWPas a reference DCI format. For example, the wireless device may monitora second DCI format in the second downlink BWP, wherein the second DCIformat may not be the reference DCI format configured. The wirelessdevice may determine a DCI size of the sidelink DCI format based on thesecond DCI format instead of the reference DCI format configured. Forexample, the wireless device may use a fallback DCI or a non-fallbackDCI as a reference DCI format in the second downlink BWP. For example,the wireless device may assume a DCI size of the reference DCI format inthe second downlink BWP is zero. The wireless device may perform a DCIsize alignment between the SL DCI format and the reference format,wherein a larger DCI size is determined based on the SL DCI format.

In an example, a wireless device may be configured with a reference DCIformat for a sidelink DCI format on an active downlink BWP of a cell fora sidelink cell. The wireless device may be configured to monitor thesidelink DCI format on a search space of the active downlink BWP of thecell. Depending on the search space and the reference DCI format, thewireless device may perform different behaviors. For example, when thewireless device is configured with a DCI format 0_0 (e.g., an uplinkscheduling DCI used for a fallback operation) for a reference DCI formatfor a sidelink DCI format in a common search space (CSS) (or thewireless device is configured to monitor the sidelink DCI on the CSS),the wireless device may determine a DCI size of the sidelink DCI formatbased on a DCI format 1_0 (e.g., a downlink scheduling DCI used for afallback operation). In a CSS, the wireless device may perform a DCIsize alignment between DCI format 0_0, 2_0, and/or 2_3 with a DCI format1_0 where a DCI size of the DCI format 1_0 is a target DCI size of all.As CSS may be shared among multiple wireless devices, it may benecessary not to change the target DCI size of DCI formats on the CSS.Embodiments provide a mechanism to maintain the target DCI size with andwithout monitoring SL DCIs based on the SL DCI format on one or moreCSSs. The wireless device may add zeros to the sidelink DCI format untilit has a same size to a size of the DCI format 1_0 monitored in the CSSor in another CSS in an active downlink BWP of a scheduling cell of asidelink cell, when the sidelink DCI format has a smaller size than thesize of DCI format 1_0. The wireless device may truncate a few bits froma most significant bits or least significant bits from the sidelink DCIformat until it has the same size to the size of the DCI format 1_0monitored in the CSS or in the another CSS in the active downlink BWP ofthe scheduling cell of the sidelink cell, when the sidelink DCI has alarger size than the size of the DCI format 1_0. In an example, when areference DCI format is a DCI format 1_0 in a CSS, the wireless devicemay align a DCI size of the sidelink DCI format to the size of the DCIformat 1_0. In an example, when a wireless device is configured tomonitor SL DCIs on one or more CSSs, the wireless device may assume areference DCI format for SL DCI formats is a DCI format 1_0. For a SLBWP, wherein a DCI size of a SL DCI format is larger than a DCI size ofthe DCI format 1_0 before truncation, the wireless device may notmonitor the SL DCI format/SL DCI on the one or more CSSs. In terms oftruncation, a wireless device may select one or more DCI fields (e.g.,Configuration index first, PUCCH resource indicator second,PSFCH-to-HARQ feedback timing indicator third, and so on) for thetruncation. When the wireless device may need to truncate all three DCIfields and may need additional truncation, this is considered as anerror case and the wireless device may not monitor SL DCIs/SL DCIformats on the one or more CSSs.

In an example, a wireless device may be configured with a reference DCIformat of a DCI format 0_0. The wireless device may have followingcases. In a first case, the wireless device may be configured to monitorthe DCI format 0_0 in one or more first common search spaces (CSSs) onlyin a current active downlink BWP. In a second case, the wireless devicemay be configured to monitor the DCI format 0_0 in one or more firstUE-specific search spaces (USSs) only in the current active downlinkBWP. In a third case, the wireless device may be configured to monitorthe DCI format 0_0 in one or more second CSSs and one or more secondUSSs in a current active downlink BWP. In the first case, the wirelessdevice may align a DCI size of the sidelink DCI format for a DCI size ofa DCI format 1_0 regardless whether the reference DCI format isconfigured either DCI format 0_0 or DCI format 1_0. In the first case,the wireless device may align the DCI size of the sidelink DCI formatbased on the DCI size of the sidelink DCI format as long as overallnumber of DCI sizes is equal to or smaller than the UE capability. Thewireless device may align a first DCI size of a first DCI format for asecond DCI size of a second DCI format by appending zeros to ortruncating a few bits from the first DCI format until a size of thefirst DCI format becomes equal to the second size. In the first case,the wireless device may determine the DCI size of the sidelink DCIformat based on the sidelink DCI format.

The wireless device may perform DCI size alignment procedure for thesidelink DCI format as illustrated in FIG. 21 . For example, when a SLDCI is configured to be monitored from a CSS (e.g., current SS is notUSS), the wireless device may perform a DCI size alignment of the SL DCIformat against one or more of DCI formats monitored on a CSS (e.g., DCIformat 1_0, 0_0, 2_0, 2_3). If a DCI size of the SL DCI format is a sameto a DCI size of DCI format 1_0 (or any other DCI format aligned withthe DCI format 1_0), no alignment is needed. The wireless device maydetermine the DCI size of the SL DCI format based on the SL DCI formatwithout further DCI alignment process. Otherwise, optionally, thewireless device may check whether the wireless device may not beconfigured with DCI formats where a number of DCI sizes before the DCIsize alignment is less than or equal to a UE capability on a schedulingcell. If the number of DCI sizes before the alignment is less than orequal to the UE capability on the scheduling cell, the wireless devicemay determine the DCI size of the SL DCI format based on the SL DCIformat. Otherwise, the wireless device may perform the DCI sizealignment. In a CSS, the wireless device may add zeros to the SL DCIformat if the DCI size of the SL DCI format before padding is smallerthan a DCI size of the DCI format 1_0. In the CSS, the wireless devicemay truncate a few bits from the SL DCI format if the DCI size of the SLDCI format before truncation is larger than the DCI size of the DCIformat 1_0. The wireless device may monitor one or more SL DCIs based onthe sidelink DCI format in the CSS based on the adjusted or determinedDCI size based on the procedure. In an example, when a wireless deviceis configured with a reference DCI format, the configuration may not beapplied for a SL DCI format monitored in a CSS. The configuration may beused to determine/perform a DCI size alignment for a SL DCI formatmonitored on a USS only. In the CSS, the wireless device may perform theDCI size alignment of the SL DCI format against a DCI format 1_0 if thewireless device is configured to monitor the SL DCI in the CSS.

For a SL DCI format configured to be monitored in a USS (e.g., YES forthe first condition in FIG. 21 ), the wireless device may check whetherthere are DCI sizes exceeding the UE capability or not before the DCIsize alignment for the SL DCI format. In case the capability is notexceeded, the wireless device may use a DCI size of the SL DCI formatwithout any adjustment. Otherwise, the wireless device may perform a DCIsize alignment between the SL DCI format and a reference DCI format. Interms of the DCI size alignment in the USS, different options mentionedin the specification may be applied. For example, the wireless devicemay add zeros to a first DCI format which has smaller size than a secondDCI format from the SL DCI format the reference DCI format. For example,the wireless device may add zeros or truncate a few bits from the SL DCIformat until the size of SL DCI format becomes equal to a DCI size ofthe reference DCI format. Based on the adjusted or determined DCI size,the wireless device may monitor SL DCIs on the USS. Note that thewireless device may be configured with a SL DCI format in one or moreUSSs and/or one or more CSSs in a downlink BWP of a scheduling cell fora sidelink cell. For each type of SS (e.g. CSS or USS), a DCI sizealignment process is performed. For example, a DCI size of a DCI formatmay be determined as a largest DCI size over the one or more USSs and/orthe one or more CSSs before any DCI size alignment. It does not precludethat a DCI size of a DCI format may be determined based only a SS wherethe DCI format is configured to be monitored.

In the second case, a wireless device may not expect to be configured tomonitor one or more sidelink DCI formats in a CSS in the active downlinkBWP. The wireless device first may determine a first DCI size for a DCIformat 0_0 in USS. The wireless device may determine a second DCI of aDCI format 1_0 in USS. The wireless device may determine a third DCIsize of a sidelink DCI format in a USS. The wireless device maydetermine a DCI size between the first, the second, and the third DCIsizes. In case, the wireless device may have a plurality of sidelink DCIformats, a largest DCI size is determined as the third DCI size. The DCIsize is used for further DCI size alignment process. For example, theDCI size is same as a DCI size of DCI format 1_0 in a CSS, a padding bitis added to the DCI format 0_0, 1_0 and the sidelink DCI format(s) inUSS. In case, the wireless device may have more DCI sizes than the UEcapability, the wireless device may perform DCI size alignment of theDCI format 0_0, 1_0 and the sidelink DCI formats for the DCI format 1_0in CSS.

The wireless device is not expected to be configured to monitor sidelinkDCI format(s) in a CSS unless the wireless device is also configured tomonitor DCI format 0_0 and 1_0 in the CSS of a BWP.

In the third case, the wireless device may perform DCI size alignment ofa first SL DCI format for the DCI format 1_0/0_0 in CSS when thewireless device is configured to monitor the first SL DCI format in CSS.The wireless device may perform DCI size alignment of a second SL DCIformat for the DCI format 1_0/0_0 in USS when the wireless device isconfigured to monitor the second SL DCI format in USS.

In an example, a wireless device may perform a DCI size alignmentprocedure differently depending on SS type (e.g., CSS or USS) where thewireless device monitors one or more sidelink DCI formats. This mayallow avoiding DCI size changes in one or more CSSs, which may degradeperformance particularly for control channels for broadcast traffic.This will minimize performance impact by reducing necessity of anytruncation in one or more USSs as truncation may lead performancedegradation.

In an example, a wireless device may be configured with a plurality ofsidelink DCI formats in a downlink BWP. The wireless device may alignDCI sizes of the plurality of the sidelink DCI formats by determining alargest DCI size of the plurality of sidelink DCI formats. The wirelessdevice may further align DCI size for a reference DCI format ifconfigured. When the wireless device is not configured to monitor thereference DCI format in an active downlink BWP, the wireless device mayassume that a DCI size of the reference DCI format is zero or a smallfixed number (e.g., M=4). The wireless device may perform DCI sizealignment between the DCI size of the reference DCI format and thealigned DCI size of the sidelink DCI format(s).

In an example, a wireless device may not expect to be configured in aCSS for a sidelink DCI format on an active downlink BWP of a schedulingcell where a DCI size of the sidelink DCI format is larger than a DCIsize of DCI format 1_0 on the active downlink BWP of the schedulingcell. The wireless device may align the sidelink DCI format for the DCIformat 1_0 in a CSS (e.g., align the sidelink DCI format against the DCIformat 1_0) regardless of configuration of a reference DCI format. In anexample, a reference DCI format may be applied only for one or moreUSSs. The wireless device may perform DCI size alignment of sidelink DCIformat(s) based on DCI format 1_0 if configured for monitoring in a CSS.

In an example, a base station may configure a reference DCI size assumedfor a sidelink DCI format regardless of an active downlink BWP of ascheduling cell for a sidelink operation for a sidelink cell via a mode1 or gNB-assisted operation. The wireless device may apply the referenceDCI size for the sidelink DCI format in a search space of the activedownlink BWP. It may be assumed that the base station may configure anumber of DCI sizes/formats accordingly such that a total number of DCIsizes needed at the current downlink BWP may not exceed UE capability.For example, the reference DCI size may be used to determine a referenceDCI format. A wireless device may select a DCI format among a pluralityof DCI formats configured to the wireless device on the active downlinkBWP excluding sidelink DCI format(s), wherein a DCI size of the DCIformat may be equal to or larger than the reference DCI size and the DCIsize of the DCI format is a smallest among DCI formats with DCI sizeslarger than or equal to the reference DCI size from the plurality of DCIformats.

For example, the wireless device may determine the reference DCI sizebased on one or more sidelink DCI formats configured in a sidelink BWPwithout explicit configuration from the base station. For example, thewireless device may take a largest DCI size of the one or more sidelinkDCI formats as the reference DCI size. For example, the wireless devicemay determine the reference DCI size based on a sidelink DCI formatconfigured in a plurality of sidelink BWPs. For example, the wirelessdevice may take a largest DCI size of the sidelink DCI format of theplurality of sidelink BWPs as the reference DCI size. For example, thewireless device may determine the reference DCI size based on one ormore sidelink DCI formats configured in a plurality of sidelink BWPs.For example, the wireless device may take a largest DCI size of the oneor more sidelink DCI formats of the plurality of sidelink BWPs as thereference DCI size.

In an example, a base station may configure a reference DCI format for asidelink DCI format for a DCI size alignment. A wireless device maydetermine a target DCI size of the sidelink DCI format based on thereference DCI format as one or more of followings: (a) the target DCIsize is a same as a DCI size of the reference DCI format. The wirelessdevice may add zeros or truncate a few bits from the sidelink DCI formatuntil the sidelink DCI format has a same size to the reference DCIformat; (b) the target DCI size is a larger value between a DCI size ofthe sidelink DCI format and the DCI size of the reference DCI format.The wireless device may add zeros to a DCI format having a smaller DCIsize between the sidelink DCI format and the reference DCI format; (c)take approach (a) or (b) depending on the reference DCI format. Forexample, if the reference DCI format is DCI format 0_0 or 1_0 or 2_0 or2_3, the approach (a) is used. If the reference DCI format is DCI forma0_1 or 1_1, the approach (b) is used; (d) take approach (a) or (b)depending on a search space monitored the sidelink DCI. For example, thewireless device may take option (a) assuming reference DCI format is DCIformat 1_0 when monitoring sidelink DCIs based on the sidelink DCIformat in a CSS. The wireless device may take option (b) otherwise; (e)first determine the target DCI size based on the sidelink DCI format.When the wireless device may have more DCI sizes to support in a currentactive DL BWP comprising search space(s) for sidelink DCIs, the wirelessdevice may apply the approach (a) and/or (b) and/or (c) and/or (d).

In an example, a wireless device may perform the DCI size alignment of asidelink DCI format only when the wireless device may monitor sidelinkDCIs and non-sidelink DCIs at a same time. For example, the wirelessdevice may perform the DCI size alignment of the sidelink DCI formatonly when the wireless device may monitor sidelink DCIs and non-sidelinkDCIs at a same search space and/or a same set of search spacecandidates.

In an example, a wireless device may be configured with a plurality ofslot offset (e.g., K3) values, wherein a sidelink DCI may schedule afirst sidelink resource based on a slot offset from the plurality ofslot offset values. The wireless device may not monitor a search spaceconfigured for monitoring sidelink DCIs where any value from theplurality of slot offset values may not indicate a sidelink resourcefrom a sidelink resource pool. The wireless device may skip monitoringsidelink DCIs in such search space.

In an example, a base station may configure a reference DCI format froma compact DCI such as DCI format 0_2 and/or DCI format 1_2. When thewireless device is configured with a reference DCI format for a sidelinkDCI format, the wireless device may first align DCI sizes of thesidelink DCI format the reference format before determining a number ofDCI sizes on an active downlink BWP. The wireless device may firstdetermine a DCI size of the sidelink DCI format in parallel when thewireless device may determine a DCI size of the reference DCI format inthe process. The wireless device may determine an aligned DCI sizebetween two DCI formats based on the alignment procedure beforeproceeding further DCI size alignment. For example, the reference DCIformat is DCI format 0_0, then the wireless device may perform the DCIsize alignment as illustrated in FIG. 22 . For example, a wirelessdevice is configured with a DCI format 0_0 or 1_0 (e.g., DCI 0) as areference DCI format for a sidelink DCI format (e.g. DCI 3). A first DCIsize of the SL DCI format is a DCI size of the SL DCI format before anyDCI size alignment. For example, the first DCI size is smaller or equalto a DCI size of DCI 0 in a first downlink BWP (BWP1). The first DCIsize is larger than a DCI size of DCI 0 in a second downlink BWP (BWP2).In the first BWP, the wireless device may add zeros to the SL DCI format(DCI 3) until it matches to the DCI 0 in terms of the size. In responseto switching to the BWP2, the wireless device may truncate a few bitsfrom the sidelink DCI format until it matches to the DCI 0. Astruncation may lead undesirable contents of the SL DCI format, thewireless device may not perform the DCI size alignment in the BWP2 orthe first DCI size of the SL DCI format is larger than a DCI size of areference DCI format when the reference DCI format is a fallback DCIformat (e.g., DCI format 0_0 or DCI format 1_0). When the wirelessdevice may not be able to truncate the bits from the SL DCI format, thewireless device may deactivate a mode 1 or a gNB-assisted operation asthere is no valid SL DCI.

In an example, when a reference DCI format is not a fallback DCI, e.g.,configured with a DCI format 0_1 or DCI format 1_1, the wireless devicemay perform a DCI size alignment of a SL DCI format and the referenceDCI format as illustrated in FIG. 23 . For example, a wireless device isconfigured with a reference format of DCI format 1 in FIG. 23 which is anon-fallback DCI format (e.g., DCI format 0_1 or DCI format 1_1). Thewireless device may perform a DCI size alignment in a first BWP (BWP1)as taking a larger DCI size between a first DCI size of the SL DCIformat and a second DCI size of the reference DCI format. The wirelessdevice may pad zeros to a smaller DCI format (e.g., DCI 3, SL DCI formatin this case0. In a second BWP (BWP2), the wireless device may add zerosto the reference DCI format (e.g., DCI 1) to align the size. In a USS,the wireless device may align DCI sizes of a plurality of DCI formatsbased on a largest DCI seize among the plurality of the DCI formats.

Example Pseudo code or a procedure of a DCI size alignment among aplurality of DCI format, particularly, considering one or more sidelinkDCI formats, is shown below. If necessary, padding or truncation may beapplied to the DCI formats according to the following actions executedin the order below:

Action 1:

-   -   Determine DCI format 0_0 monitored in a common search space        according to clause 7.3.1.1.1 where is the size of the initial        UL bandwidth part.    -   Determine DCI format 1_0 monitored in a common search space        according to clause 7.3.1.2.1 where is given by        -   the size of CORESET 0 if CORESET 0 is configured for the            cell; and        -   the size of initial DL bandwidth part if CORESET 0 is not            configured for the cell.        -   If DCI format 0_0 is monitored in common search space and if            the number of information bits in the DCI format 0_0 prior            to padding is less than the payload size of the DCI format            1_0 monitored in common search space for scheduling the same            serving cell, a number of zero padding bits are generated            for the DCI format 0_0 until the payload size equals that of            the DCI format 1_0.        -   If DCI format 0_0 is monitored in common search space and if            the number of information bits in the DCI format 0_0 prior            to truncation is larger than the payload size of the DCI            format 1_0 monitored in common search space for scheduling            the same serving cell, the bitwidth of the frequency domain            resource assignment field in the DCI format 0_0 is reduced            by truncating the first few most significant bits such that            the size of DCI format 0_0 equals the size of the DCI format            1_0.            -   If a UE monitors DCI format 3_0 and 3_1 in a search                space and the number of information bits in the DCI                format 3_0 prior to padding is less than the payload                size of the DCI format 3_1 for the same scheduling cell,                a number of zero padding bits are generated for the                smaller DCI format 3_0 until the payload size equal to                the larger DCI format 3_1.            -   If a UE monitors DCI format 3_0 and 3_1 in a search                space and the number of information bits in the DCI                format 3_1 prior to padding is less than the payload                size of the DCI format 3_0 for the same scheduling cell,                a number of zero padding bits are generated for the                smaller DCI format 3_1 until the payload size equal to                the larger DCI format 3_O.            -   (a) If DCI format 3_0 and/or 3_1 is monitored in common                search space, a UE is not expected that the number of                information bits in the DCI format 3_0 and/or 3_1 prior                to truncation is larger than the payload size of the DCI                format 1_0 monitored in common search space for                scheduling the same serving cell.

Referring to the example pseudo code above, a wireless device maydetermine a first DCI size of a DCI format. When a wireless device isconfigured with a first sidelink DCI format (e.g., DCI format 3_0) and asecond sidelink DCI format (e.g., DCI format 3_1) in a downlink BWP of ascheduling cell for a sidelink cell, the wireless device first determinea DCI size of the first and second sidelink DCI format by taking alarger DCI size between them. For example, if a first DCI size of thefirst SL DCI format is larger than a second DCI size of the second SLDCI format, the wireless device may add zeros to the second DCI formatuntil sizes match between them. Otherwise, the wireless device may addzeros to the first DCI format until sizes match between them. Theprocedures are shown in FIG. 24 in underlined texts. When a wirelessdevice is configured with DCI format 3_0 and/or DCI format 3_1 forsidelink DCI(s) in a first CSS, the wireless device may not expect thata first DCI size of the DCI format 3_0 and/or a second DCI size of theDCI format 3_1 may be larger than a DCI size of DCI format 1_0 in asecond CSS. The first CSS and the second CSS may be a same or may bedifferent. This is shown in (a) text in FIG. 24 .

Example Pseudo code for a second action is shown below.

Action 2:

-   -   Determine DCI format 0_0 monitored in a UE-specific search space        according to clause 7.3.1.1.1 where is the size of the active UL        bandwidth part.    -   Determine DCI format 1_0 monitored in a UE-specific search space        according to clause 7.3.1.2.1 where is the size of the active DL        bandwidth part.    -   For a UE configured with supplementary Uplink in        ServingCellConfig in a cell, if PUSCH is configured to be        transmitted on both the SUL and the non-SUL of the cell and if        the number of information bits in DCI format 0_0 in UE-specific        search space for the SUL is not equal to the number of        information bits in DCI format 0_0 in UE-specific search space        for the non-SUL, a number of zero padding bits are generated for        the smaller DCI format 0_0 until the payload size equals that of        the larger DCI format 0_0.    -   If DCI format 0_0 is monitored in UE-specific search space and        if the number of information bits in the DCI format 0_0 prior to        padding is less than the payload size of the DCI format 1_0        monitored in UE-specific search space for scheduling the same        serving cell, a number of zero padding bits are generated for        the DCI format 0_0 until the payload size equals that of the DCI        format 1_0.    -   If DCI format 1_0 is monitored in UE-specific search space and        if the number of information bits in the DCI format 1_0 prior to        padding is less than the payload size of the DCI format 0_0        monitored in UE-specific search space for scheduling the same        serving cell, zeros shall be appended to the DCI format 1_0        until the payload size equals that of the DCI format 0_0

(b) Action 2A:

-   -   If a reference DCI format for a DCI format 3_0 and/or DCI format        3_1 is a DCI format 0_0 and/or DCI format 1_0 in USS and if the        number of information bits in the DCI format 3_0 and/or DCI        format 3_1 prior to padding is less than the payload size of the        DCI format 0_0 monitored in UE-specific search space for        scheduling the same serving cell, a number of zero padding bits        are generated for the DCI format 3_0 and/or DCI format 3_1 until        the payload size equals that of the DCI format 0_0.    -   If a reference DCI format for a DCI format 3_0 and/or DCI format        3_1 is a DCI format 0_0 and/or DCI format 1_0 in USS and if the        number of information bits in the DCI format 0_0 and DCI format        1_0 prior to padding is less than the payload size of the DCI        format 3_0 and/or DCI format 3_1 monitored in UE-specific search        space for scheduling the same serving cell, a number of zero        padding bits are generated for the DCI format 0_0 and DCI format        1_0 until the payload size equals that of the DCI format 3_0        and/or DCI format 3_1.    -   [If the size of DCI format 0_2 monitored in a UE-specific search        space equals that of a DCI format 0_0/1_0 monitored in another        UE-specific search space, one bit of zero padding shall be        appended to DCI format 0_2.]    -   [If the size of DCI format 1_2 monitored in a UE-specific search        space equals that of a DCI format 0_0/1_0 monitored in another        UE-specific search space, one bit of zero padding shall be        appended to DCI format 1_2.]

Referring to the example pseudo code above, a wireless device may beconfigured with a reference DCI format as a DCI format 0_0 or DCI format1_0 and the wireless device may be configured to monitor SL DCIs on aUSS. The wireless device may perform a DCI size alignment between the SLDCI format(s) and the reference DCI format. (b) Action 1A. The wirelessdevice may add zeros to a smaller DCI format between a sidelink DCIformat and the reference DCI format until sizes of both match.

Example Pseudo code for a third action is shown below.

Action 3:

-   -   Determine DCI format 0_1 monitored in a UE-specific search space        according to clause 7.3.1.1.2.    -   Determine DCI format 1_1 monitored in a UE-specific search space        according to clause 7.3.1.2.2.    -   For a UE configured with supplementary Uplink in        ServingCellConfig in a cell, if PUSCH is configured to be        transmitted on both the SUL and the non-SUL of the cell and if        the number of information bits in format 0_1 for the SUL is not        equal to the number of information bits in format 0_1 for the        non-SUL, zeros shall be appended to smaller format 0_1 until the        payload size equals that of the larger format 0_1.    -   If the size of DCI format 0_1 monitored in a UE-specific search        space equals that of a DCI format 0_0/1_0 monitored in another        UE-specific search space, one bit of zero padding shall be        appended to DCI format 0_1.    -   If the size of DCI format 1_1 monitored in a UE-specific search        space equals that of a DCI format 0_0/1_0 monitored in another        UE-specific search space, one bit of zero padding shall be        appended to DCI format 1_1.

(b) Step 2-0A:

-   -   If a reference DCI format for a DCI format 3_0 and/or DCI format        3_1 is a DCI format 0_1 in USS and if the number of information        bits in the DCI format 3_0 and/or DCI format 3_1 prior to        padding is less than the payload size of the DCI format 0_0        monitored in UE-specific search space for scheduling the same        serving cell, a number of zero padding bits are generated for        the DCI format 3_0 and/or DCI format 3_1 until the payload size        equals that of the DCI format 0_1.    -   If a reference DCI format for a DCI format 3_0 and/or DCI format        3_1 is a DCI format 0_1 ain USS and if the number of information        bits in the DCI format 0_1 prior to padding is less than the        payload size of the DCI format 3_0 and/or DCI format 3_I        monitored in UE-specific search space for scheduling the same        serving cell, a number of zero padding bits are generated for        the DCI format 0_1 until the payload size equals that of the DCI        format 3_0 and/or DCI format 3_1.

[similar behavior for DCI format 1_0 case]

-   -   [If the size of DCI format 0_2 monitored in a UE-specific search        space equals that of a DCI format 0_0/1_0 monitored in another        UE-specific search space, one bit of zero padding shall be        appended to DCI format 0_2.]    -   [If the size of DCI format 1_2 monitored in a UE-specific search        space equals that of a DCI format 0_0/1_0 monitored in another        UE-specific search space, one bit of zero padding shall be        appended to DCI format 1_2.]

[similar behavior when a reference DCI format is either DCI format 0_2or 1_2]

Referring to the example pseudo code above, a reference DCI format is anon-fallback DCI (e.g., a DCI format 0_1 or 1_1) is illustrated. Similarto a DCI format 1_0 and 0_0 in a USS case, the wireless device mayperform the DCI size alignment between SL DCI format(s) and thereference DCI format by adding zeros to a smaller DCI format(s).

In an example, a wireless device may be configured with a multiple TRP(transmission point and reception) or a plurality of CORESET pools for ascheduling cell for sidelink DCIs for a sidelink cell. The wirelessdevice may be configured with a reference DCI format in an activedownlink BWP of the scheduling cell. The wireless device may apply a DCIsize alignment of a sidelink DCI format based on the reference DCIformat, wherein a DCI size of the reference DCI format may bedetermined. For example, the DCI size of the reference DCI format may bedetermine based on one or more search spaces of a CORESET pool whereinthe wireless device is configured to monitor sidelink DCIs on theCORESET pool. When the wireless device monitors sidelink DCIs in a firstCORESET pool (e.g., CORESET pool id=0, or not configured with a CORESETpool ID, etc.), the wireless device may determine the DCI size based onsearch spaces of the first CORESET pool. Similarly, a second DCI size ofa sidelink DCI format may be also determined based on one or more secondsearch spaces of the CORESET pool. For example, the DCI size of thereference DCI format may be determine based on one or more search spacesof one or more CORESET pools of the active downlink BWP of the cell. Thewireless device may determine a largest DCI size of DCI sizes of thereference DCI format on the one or more search spaces of the one or moreCORESET pools of the active downlink BWP of the cell.

In an example, a base station may transmit one or more radio resourcecontrol (RRC) messages indicating configuration parameters. Theconfiguration parameters may indicate enabling a sidelink mode 1operation. In the sidelink mode 1 operation, a wireless device mayreceive sidelink DCIs (SL-DCIs). Each SL-DCI may comprise resourceassignment(s) for one or more sidelink transmissions.

In existing technologies, a sidelink DCI may comprise one or moreresource assignment(s) of one or more sidelink transmissionscorresponding to a sidelink transport block. For example, the sidelinkDCI may indicate a resource for a single sidelink transmission. Forexample, the sidelink DCI indicates a plurality of resources for initialand retransmission of a transport block. The plurality of resources maycomprise frequency resources in a plurality of time resources (e.g., atime resource may correspond to a sidelink slot, a OFDM symbol, a slot,and/or like). In existing technologies, the configuration parameters mayindicate one or more parameters of a configured grant configuration fora sidelink operation. The one or more parameters may comprise aperiodicity where configured grant resource may occur periodically basedon the periodicity. An activation DCI may comprise resource assignmentfor the configured grant configuration. The wireless device maydetermine a resource (e.g., a time/frequency resource) based on theactivation DCI. The wireless device may determine periodic resources ofthe configured grant configuration based on the resource indicated bythe activation DCI and the periodicity configured by one or more RRCmessages.

In existing mechanisms, the wireless device determines a periodicity ofa configured grant configuration based on RRC configurationparameter(s). In sidelink operation, traffic patterns include periodictraffic and aperiodic traffic. Existing mechanisms of a configured grantconfiguration may address a need of periodic traffics well. Yet,existing mechanisms may not effectively address aperiodic traffic. Forexample, once aperiodic traffic occurs, the wireless device may requirea plurality of resource assignments with burstiness of the traffic. Inexisting mechanisms, the base station may transmit a plurality ofsidelink DCIs scheduling a plurality of resources for a plurality oftransport blocks. This may increase latency of scheduling to handleaperiodic traffic. This also increases signaling overhead between thebase station and the wireless device.

In an example, a wireless device may receive a sidelink DCI comprising afirst set of resources and a periodicity. In response to the receiving,the wireless device may determine sidelink resources from a sidelinkresource pool for one or more sidelink transmissions based on the firstset of resources and the periodicity. The first set of resources and theperiodicity from the sidelink DCI may be carried over a sidelink controlinformation (SCI) via a sidelink control channel (e.g., PSCCH) to one ormore receiver wireless devices. In response to receiving the SCI, theone or more receivers may expect one or more (re)transmission of a firstTB via the first set of resources. The one or more receivers may alsodetermine reservation of one or more resources based on the first set ofresources and/or the periodicity.

In an example, the wireless device may determine a second set ofresources based on the first set of resources and the periodicity (e.g.,same frequency resources and time resources with the periodicity gapbetween the first and the second set of resources). The wireless devicemay use the second set of resources unless the base station may transmitanother sidelink DCI indicating a third set of resources where the thirdset of resources may occur approximately after the periodicity from thefirst set of resources. A similar behavior may be repeatedly applied ina set of times (e.g., T0 indicated by the first set of resources,T1=T0+the periodicity, T2=T0*2*the periodicity, . . . , etc.).

In an example, the wireless device may activate a configured grantresource in response to receiving the sidelink DCI comprising theperiodicity where the periodicity value is not zero. The wireless devicemay release the configured grant resource in response to receivinganother sidelink DCI indicating a same configured grant resource,wherein the another sidelink DCI comprises zero periodicity or notcomprising a periodicity. For aperiodic traffic pattern, a wirelessdevice may have a short-term burst traffic where the one or moreconfigured grant resources may be needed in the short-term with a shortperiodicity. Utilizing RRC configurations of one or more configuredgrant resources and activation/releasing via one or more DCIs may lead ahigh overhead, particularly for configured grant resources used for ashort-term burst aperiodic traffic.

A base station may utilize a normal sidelink DCIs comprising periodicityand resource assignments to activate and reactivate one or moreconfigured grants with and without prior RRC configurations of the oneor more configured grants. Embodiments may allow a low overheadmechanism to activate one or more configured grant resources, mainlyneeded for aperiodic traffic patterns. Example embodiments allow asingle sidelink DCI scheduling a plurality of resources for a pluralityof sidelink transport blocks. These allow a low signaling overhead and alow latency.

In an example, a wireless device may receive a sidelink DCI comprising afirst set of resources and a periodicity. In response to the receiving,the wireless device may determine sidelink resources from a sidelinkresource pool for one or more sidelink transmissions based on the firstset of resources and the periodicity. The first set of resources and theperiodicity from the sidelink DCI may be carried over a sidelink controlinformation (SCI) via a sidelink control channel (e.g., PSCCH) to one ormore receiver wireless devices. In response to receiving the SCI, theone or more receivers may expect one or more (re)transmission of a firstTB via the first set of resources. The one or more receivers may alsodetermine reservation of one or more resources based on the first set ofresources and/or the periodicity.

When the wireless device receives the sidelink DCI comprising theperiodicity, the wireless device may interpret resource assignment by abase station as one or more of the following options. Option A is asfollows. The indicated periodicity is used only for the SCItransmission. Unless the wireless device receives another sidelink DCIafter the periodicity from the first set of resources, the wirelessdevice may not assume any further sidelink resources allocated by thesidelink DCI except for the first set of resources. The wireless devicemay use the periodicity for determining a reservation periodicitycarried over a sidelink control information (SCI) transmitted with oneor more sidelink transmissions via the first set of resources. The oneor more sidelink transmissions may transmit initial and/orretransmission of a sidelink transport block.

Option B is as follows. The wireless device may determine a second setof resources based on the first set of resources and the periodicity(e.g., same frequency resources and time resources with the periodicitygap between the first and the second set of resources). The wirelessdevice may use the second set of resources unless the base station maytransmit another sidelink DCI indicating a third set of resources wherethe third set of resources may occur approximately after the periodicityfrom the first set of resources. A similar behavior may be repeatedlyapplied in a set of times (e.g., TO indicated by the first set ofresources, T1=T0+the periodicity, T2=T0*2*the periodicity, . . . ,etc.). Overriding SL DCIs may be received approximately after multipleof the periodicity from the first set of time resources. The wirelessdevice may use the periodicity for determining a reservation periodicitycarried over a sidelink control information (SCI) transmitted with oneor more sidelink transmissions via the first set of resources. Thewireless device may use the periodicity for determining a secondreservation periodicity carried over a second SCI transmitted with oneor more second sidelink transmissions via the second set of resources.The one or more sidelink transmissions may transmit initial and/orretransmission of a sidelink transport block. The one or more secondsidelink transmissions may transmit/carry initial and/or retransmissionof a second sidelink transport block. The second sidelink transportblock may be different from the sidelink transport block.

Option C is as follows. The wireless device may activate a configuredgrant resource in response to receiving the sidelink DCI comprising theperiodicity where the periodicity value is not zero. The wireless devicemay release the configured grant resource in response to receivinganother sidelink DCI indicating a same configured grant resource,wherein the another sidelink DCI comprising zero periodicity or notcomprising a periodicity. For aperiodic traffic pattern, a wirelessdevice may have a short-term burst traffic where the one or moreconfigured grant resources may be needed in the short-term with a shortperiodicity. Utilizing RRC configurations of one or more configuredgrant resources and activation/releasing via one or more DCIs may lead ahigh overhead, particularly for configured grant resources used for ashort-term burst aperiodic traffic. A base station may utilize a normalsidelink DCIs comprising periodicity and resource assignments toactivate and reactivate one or more configured grants with and withoutprior RRC configurations of the one or more configured grants.Embodiments may allow a low overhead mechanism to activate one or moreconfigured grant resources, mainly needed for aperiodic trafficpatterns.

FIG. 24 illustrates an example of a SL DCI scheduling a first set ofresources and a periodicity. In a time n, a wireless device may transmita sidelink scheduling request (SR) in response to new sidelink dataarrival at UE's (e.g., the wireless device's) MAC layer. A base station,in response to receiving the SL SR, may transmit a sidelink DCIcomprising the first set of resources for a first PSSCH (e.g., PSSCH #1)and a second PSSCH (e.g., PSSCH #2), and the periodicity. For example,the first PSSCH and the second PSSCH may be used for a first transportblock. The wireless device may determine a second set of resources (fora third PSSCH (e.g., PSSCH #3) and a potentially fourth PSSCH (e.g.,PSSCH #4)) based on the first set of resources and the periodicity.Based on the second set of resources, the wireless device may transmitthe third PSSCH and/or the fourth PSSCH. For example, the third PSSCHand the fourth PSSCH may be used for a second transport block. Forexample, the wireless device may transmit each transport block of aplurality of transport blocks over one or more resources indicated by asidelink DCI and a periodicity (e.g., a first transport block via afirst set of resources indicated by a sidelink DCI, a second transportblock via a second set of resources determined based on the first set ofresources and a periodicity, and so on).

The wireless device may determine the second set of resources whereinthe second set of resources may have a same set of frequency resourcesto the first set of resources and a time offset between the first set ofresources and the second set of resources in time domain is theperiodicity. Additionally, the wireless device may determine a third setof resources with 2*the periodicity, and a fourth set of resources with3*the periodicity and so on. The wireless device may transmit differenttransport blocks via different set of resources based on the first setof resources and the periodicity. For example, the wireless device maytransmit one or more transport blocks via a plurality of sets ofresources based on the first set of resources and the periodicity. Thewireless device may apply activation mechanism specified in thisspecification based on the SL DCI for a duration if configured/indicatedor until the wireless device may receive release/deactivationindication.

FIG. 25 illustrates a flow diagram of an example embodiment. Forexample, a sidelink DCI may indicate an activation or deactivation of aconfigured grant configuration. A base station may transmit one or moreRRC messages indicating configuration parameters of a configured grantconfiguration. The configuration parameters may comprise spatial filterparameter of the configured grant configuration and parameters oftransmission such as bundling and hopping. The configuration parametersmay not indicate a periodicity of the configured grant configuration.The configuration parameters may not indicate time/frequency resourcesof a first configured grant resource of the configured grantconfiguration. The base station may transmit a sidelink DCI indicatingtime/frequency resource(s) for configured grant resource(s) of theconfigured grant configuration and indicating a periodicity fordetermining successive/periodic configured grant resources of theconfigured grant configuration. In FIG. 25 , the wireless devicereceives a sidelink DCI (SL DCI). The wireless device may determinewhether a value of a periodicity indicated by the SL DCI is larger thanzero or is equal to zero. For example, the value of the periodicity maybe used to either activate or deactivate the configured grantconfiguration. For example, the periodicity being larger than zero mayindicate an activation of the configured grant configuration. Forexample, the periodicity being equal to zero may indicate andeactivation of the configured grant configuration. The periodicitybeing larger than zero may override a first periodicity configured inthe configured grant configuration. In this case, the configurationparameters may indicate a first periodicity of the configured grantconfiguration. The periodicity of the SL DCI may update or override thefirst periodicity of the configured grant configuration.

Based on the value of the periodicity, for example, when the value islarger than zero, the wireless device activates the configured grantconfiguration. The wireless device may determine the configured grantconfiguration of a plurality of configured grant configurations based ona HARQ process ID indicated by the SL DCI. The wireless device mayactivate the determined configured grant configuration based on (inresponse to) the periodicity being larger than zero. Similarly, when theperiodicity is zero, the wireless device may determine the configuredgrant configuration based on the HARQ process ID indicated by the SLDCI. The wireless device may deactivated the determined configured grantconfiguration. The wireless device may transit one or more sidelinktransmissions via PSSCHs based on resources indicated by the SL DCI.

In an example, a wireless device is configured with one or moreconfigured grant resources, wherein each configured grant may comprise aperiodicity and/or an offset. The wireless device may receive a SL DCIactivating at least a configured grant resource. The activating SL DCImay comprise a first set of resources and a periodicity. In response toreceiving the activating SL DCI, the wireless device may activate theconfigured grant resource as an initial resource occurs at the first setof resources, and successive resources occur at a multiple of theperiodicity. The periodicity in the activating SL DCI, if indicated orindicated as non-zero value, may override the periodicity in theconfigured grant. Alternatively, a base station may not configure theperiodicity and/or the offset in the configured grant resource. Theperiodicity and/or the offset may be indicated via the activating SLDCI.

In an example, a wireless device may interpret a SL DCI as an activationSL DCI for a configured grant when one or more following conditions aremet. First, NDI field is set to ‘1’ or a predefined value (e.g., 1). Thewireless device may differentiate between an activation SL DCI and arelease SL DCI based on a time gap value. For example, NDI=1 and timegap value is non-zero are considered as an activation based onSL-CS-RNTI. NDI=1 and time gap value is zero are considered as anrelease based on SL-CS-RNTI.

Interpreting a SL DCI as an activation of at least a configured grantresource may be assumed in an unlicensed scheduling cell wherescheduling may not occur periodically due to medium access.

In an example, an activation SL DCI or a SL DCI comprising a periodicityfor activating a configured grant resource may indicate a validitycounter. A wireless device may be configured with a plurality ofvalidity counter values and one value from the plurality of the validitycounter values may be indicated in the SL DCI. The wireless device mayuse up to the validity counter of the configured grant resource. Thewireless device may reset a transmission counter in response toreceiving the SL DCI activating the configured grant resource. Thewireless device may increment the transmission counter in everyperiodicity. The wireless device may deactivate or release or suspendthe configured grant when the transmission counter reaches the validitycounter.

The validity counter may be indicated/configured by the base station orselected by the wireless device randomly. In an example, a base stationmay configure one or more configured grant resources via RRC signaling,wherein the one or more configured grant resources may be activatedand/or released via SL DCIs as specified in this specification.

In an example, a wireless device may receive one or more radio resourcecontrol (RRC) messages. The one or more RRC messages may indicate areference downlink control information (DCI) format for each of aplurality of downlink bandwidth part (BWP) of a scheduling cell for asidelink cell. The wireless device may determine a DCI size of asidelink (SL) DCI format at least based on an active downlink BWP of thescheduling cell from the plurality of downlink BWPs and a reference DCIformat corresponding to the active downlink BWP. The wireless device mayreceive a sidelink DCI having the determined DCI size on the activedownlink BWP of the scheduling cell.

For example, the wireless device may be configured with a DCI format 1_0as the reference format for the SL DCI format monitored in a first CSS.The wireless device may append zeros to the SL DCI format when the SLDCI format has a smaller DCI size compared to a DCI size of the DCIformat 1_0 wherein the wireless device may monitor the DCI format 1_0 ina second CSS. The wireless device may assume that the SL DCI format ofthe first CSS is not larger than the DCI size of the DCI format 1_0 ofthe second CSS. The wireless device may use a same DCI size between theSL DCI format and the DCI format 1_0 when the SL DCI format isconfigured in the first CSS. The first CSS may be same as the secondCSS, or may be different from the second CSS.

For example, the wireless device may be configured with a DCI format 1_0or 0_0 as the reference format for a SL DCI format monitored in a firstUSS. The wireless device may determine a target DCI size of the SL DCIformat based on the DCI format 1_0, DCI format 0_0 and the SL DCI formatin the USS. For example, the wireless device may select a DCI formatamong the SL DCI format, the DCI format 1_0, DCI format 0_0 wherein aDCI size is a largest among them. The wireless device may append zerosto non-selected DCI format(s) until a same DCI size to the selected DCIis reached. The wireless device may align DCI sizes of the SL DCIformat, DCI format 0_1, and DCI format 0_0 based on zero-padding ifneeded.

For example, the wireless device may be configured with a DCI format 0_2or 1_2 as the reference format for a SL DCI format monitored in a secondUSS. The wireless device may determine a DCI size of the SL DCI formatbased on the DCI format 0_2, DCI format 1_2 and the SL DCI format in theUSS. For example, the wireless device may select a DCI format among theSL DCI format, the DCI format 0_2, DCI format 1_2 wherein a DCI size isa largest among them. The wireless device may add zeros to non-selectedDCI format(s) until a same DCI size to the selected DCI is reached. Thewireless device may align DCI sizes of the SL DCI format, the DCI format0_2, and the DCI format 1_2 based on zero-padding if needed.

For example, the wireless device performs the DCI size alignment betweenthe SL DCI format and the DCI format 1_1 or between the SL DCI formatand the DCI format 1_0, when the wireless device is not configured tomonitor the DCI format 0_2 and/or DCI format 1_2. For example, thewireless device performs the DCI size alignment between the SL DCIformat, the DCI format 1_1 and the DCI format 1_0, when the wirelessdevice is configured to monitor the DCI format 0_2 and/or DCI format1_2.

For example, the wireless device may be configured with a DCI format 0_1as the reference format for a SL DCI format monitored in a second USS.The wireless device may add zeros to the SL DCI format when the SL DCIformat is smaller than the DCI format 0_1 before the padding. Thewireless device may add zeros to the DCI format 0_1 when the DCI forma0_1 is smaller than the DCI format 0_1 before the padding. A similarbehavior is applied when the wireless device is configured with a DCIformat 1_1 as a reference DCI format. In case the wireless device maymonitor DCI format 0_2 and/or 1_2 in the active downlink BWP, thewireless device may perform a similar DCI alignment procedure betweenDCI format 0_1, DCI format 1_1 and the SL DCI format.

The wireless device may be indicated by the base station with a firstreference DCI format for a SL DCI format, wherein the first referenceDCI format is used for the SL DCI format monitored in one or more commonsearch spaces (CSS). For example, the first reference DCI format isassumed as DCI format 1_0 when the first reference DCI format is notexplicitly configured. The wireless device may be indicated by the basestation with a second reference DCI format for the SL DCI format,wherein the second reference DCI format is used for the SL DCI formatmonitored in one or more UE-specific search spaces (USS). For example,the second reference DCI format may be configured via RRC signaling. Thefirst reference DCI format may be assumed without an RRC message.

For example, the wireless device may perform a DCI size alignmentprocess in response to switching a uplink BWP or a downlink BWP of thescheduling cell

In an example, a wireless device may determine a first downlinkinformation (DCI) size of a SL DCI format based on a first SL BWP, afirst downlink BWP and a first reference DCI format. The wireless devicemay monitor the SL DCI format based on the first DCI size on the firstdownlink BWP. The wireless device may switch an active downlink BWP fromthe first downlink BWP to a second downlink BWP. The wireless device maydetermine a second DCI size of the SL DCI format based on the firstsidelink BWP, the second downlink BWP and a second reference DCI format.The wireless device may monitor the sidelink DCI format based on thesecond DCI size on the second downlink BWP.

In an example, a wireless device may receive a SL DCI comprising one ormore first frequency resources, one or more time resources and aperiodicity. The wireless device may determine a first set of sidelinkresources based on the one or more first frequency resources and the oneor more first time resources. The wireless device may determine a secondset of sidelink resources based on the one or more first frequencyresources, the one or more first time resources and the periodicity. Thewireless device may transmit one or more first sidelink transmissionsvia the first set of sidelink resources in response to the receiving theSL DCI. The wireless device may transmit one or more second sidelinktransmissions via the second set of sidelink resources based on the SLDCI.

In an example, a wireless device may receive a SL DCI comprising one ormore first frequency resources, one or more time resources and aperiodicity. In response to receiving the SL DCI with the periodicitygreater than zero, the wireless device may activate a configured grantresources, wherein the configured grant resources are determined basedon the one or more first frequency resources for frequency domainresources and base on the one or more first time resources and theperiodicity for time domain resources. The wireless device may applyactivation of the configured grant resource in response to the receivingthe SL DCI with the periodicity being greater than zero.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 26 is an flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 2610, a wireless device may receive asidelink (SL) downlink control information (DCI). The SL DCI mayindicate: one or more first frequency domain resources; one or morefirst time domain resources; and a periodicity. At 2620, one or more SLcontrol information (SCI) may be transmitted via a first set of SLresources. The one or more SCI may indicate the periodicity and one ormore first SL transmissions. The first set of SL resources may bedetermined based on the one or more first frequency domain resources andthe one or more first time domain resources. At 2630, one or more secondSL transmissions may be transmitted via a second set of SL resources.The second set of SL resources may be determined based on: the one ormore first frequency domain resources; the one or more first time domainresources; and the periodicity.

According to an example embodiment, the wireless device may determine athird set of SL resources based on: the one or more first frequencydomain resources; the one or more first time domain resources; and anumber of the periodicity. According to an example embodiment, thenumber of the periodicity may be incremented by 1 in each set of SLresources. According to an example embodiment, a physical SL controlchannel may carry the SCI. According to an example embodiment, the oneor more first SL transmissions may carry a first SL transport block.According to an example embodiment, the wireless device may transmit orretransmit the first SL transport block via the first set of SLresources. According to an example embodiment, the one or more second SLtransmissions may carry a second SL transport block. According to anexample embodiment, the wireless device may transmit or retransmit thesecond SL transport block via the second set of SL resources. Accordingto an example embodiment, the first SL transport block may be differentfrom the second SL transport block.

The invention claimed is:
 1. A method comprising: receiving, by awireless device, downlink control information (DCI) indicating: a set ofperiodic resources for sidelink (SL) transmissions; and a periodicity ofthe periodic resources; in response to the receiving of the DCI,resetting a transmission counter for counting a number of the SLtransmissions; transmitting, via the set of periodic resources and basedon the periodicity, one or more SL transmissions of the SLtransmissions; and in response to the transmitting the one or more SLtransmissions, incrementing a value of the transmission counter by avalue of a counter step after each periodicity.
 2. The method of claim1, wherein one or more first SL transmissions, of the SL transmissions,carry a first SL transport block.
 3. The method of claim 2, furthercomprising transmitting or retransmitting the first SL transport blockvia one or more first resources of the set of periodic resources.
 4. Themethod of claim 3, wherein one or more second SL transmissions, of theSL transmissions, carry a second SL transport block.
 5. The method ofclaim 4, further comprising transmitting or retransmitting the second SLtransport block via one or more second resources of the set of periodicresources.
 6. The method of claim 5, wherein the first SL transportblock is different from the second SL transport block.
 7. The method ofclaim 1, wherein sidelink control information (SCI) of the SLtransmissions indicates the periodicity.
 8. The method of claim 1,wherein the DCI indicates a counter value indicating a maximum number ofone or more SL transmissions of the SL transmissions.
 9. The method ofclaim 8, further comprising stopping the SL transmissions based on thetransmission counter reaching the counter value.
 10. The method of claim1, further comprising determining, based on the periodicity, successiveresources of the set of periodic resources in a time domain.
 11. Awireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive downlink control information (DCI)indicating: a set of periodic resources for sidelink (SL) transmissions;and a periodicity of the periodic resources; in response to thereceiving of the DCI, reset a transmission counter for counting a numberof the SL transmissions; transmit, via the set of periodic resources andbased on the periodicity, one or more SL transmissions of the SLtransmissions; and in response to the transmitting the one or more SLtransmissions, increment a value of the transmission counter by a valueof a counter step after each periodicity.
 12. The wireless device ofclaim 11, wherein one or more first SL transmissions, of the SLtransmissions, carry a first SL transport block.
 13. The wireless deviceof claim 12, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to transmit or retransmitthe first SL transport block via one or more first resources of the setof periodic resources.
 14. The wireless device of claim 13, wherein oneor more second SL transmissions, of the SL transmissions, carry a secondSL transport block.
 15. The wireless device of claim 14, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to transmit or retransmit the second SL transportblock via one or more second resources of the set of periodic resources.16. The wireless device of claim 15, wherein the first SL transportblock is different from the second SL transport block.
 17. The wirelessdevice of claim 11, wherein the DCI indicates a counter value indicatinga maximum number of one or more SL transmissions of the SLtransmissions.
 18. The wireless device of claim 17, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to stop the SL transmissions based on thetransmission counter reaching the counter value.
 19. The wireless deviceof claim 11, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to determine, based on theperiodicity, successive resources of the set of periodic resources in atime domain.
 20. A system comprising: a base station; and a wirelessdevice comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive downlink control information (DCI)indicating: a set of periodic resources for sidelink (SL) transmissions;and a periodicity of the periodic resources; in response to thereceiving of the DCI, reset a transmission counter for counting a numberof the SL transmissions; transmit, via the set of periodic resources andbased on the periodicity, one or more SL transmissions of the SLtransmissions; and in response to the transmitting the one or more SLtransmissions, increment a value of the transmission counter by a valueof a counter step after each periodicity.